feat(pin): invalidate persistent tokens on rejection and PIN change (4/5)#234
Merged
Conversation
This was referenced May 30, 2026
e150a60 to
0fee3aa
Compare
3c1df1f to
bed6c79
Compare
0fee3aa to
b16de46
Compare
ada22af to
f38d6ee
Compare
b16de46 to
e36c0cf
Compare
f38d6ee to
35f9add
Compare
e36c0cf to
47a76d0
Compare
35f9add to
7e7f379
Compare
47a76d0 to
682e81f
Compare
7e7f379 to
2fc406f
Compare
682e81f to
a680927
Compare
2fc406f to
0283638
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part 4 of 5 in a stack: #231, #232, #233, #234 (this), #235
This stack adds support for persistent pinUvAuthTokens (the CTAP 2.2+
pcmrpermission), so a credential manager can list passkeys without re-prompting for the PIN on every launch or replug. Read-only credential management only.This PR
Keeps stored tokens fresh: